I added a little delay effect

I don't understand

I added a little delay effect

I don't understand

lol it was a joke, I just added a 3 second promise before showing the success to better simulate the real thing for the sake of QA 😂

Doesn't work

https://blockscan.com/Error/404

We do indeed get the hash and it doesn't change from it being sent and it being confirmed afaik. So I think either Blockscan doesn't have it yet and returns a 404 or there is some other issue, likely it hadn't populated yet. Idk if you'll agree but explorers tend to hold the tx until it is confirmed, perhaps Blockscan is different.

I will think more on your comment and include this attempted optimization (properly implemented if it's doable) alongside any others. I'll aim to have a PR open for this over the weekend.

Was it the preview deployment that you tested I assume?

Would you be able to share the PK for the wallet used for the preview deployments with me?

It was merged to production and I claimed and tested. You should run locally and claim/test